Chip 2000 October

home *** CD-ROM | disk | FTP | other *** search

/ Chip 2000 October / CHIP Turkiye Ekim 2000.iso / prog / share / 53 / Readme.txt < prev next >

Wrap

Text File | 1999-07-02 | 18.0 KB | 475 lines

Miramar Systems, Inc. PC MACLAN version 7.2 ----------------------------------------------------------------------------- This document may contain information not found in the manual. Please read. ----------------------------------------------------------------------------- C O N T E N T S I. Installing II. Running in Demo mode III. Upgrading from Personal MACLAN v5.5x or PC MACLAN v6.x/v7.x IV. Unlisted Adapters Information (ODI & NDIS3) V. Errors during Installation VI. Errors during operation VII. Incompatible Network Adapters VIII. Performance Issues IX. AFP 2.2 and Reporting available disk space on large drives X. Uninstalling ============================================================================= I. Installing to Windows 95/98 A.Run Install from DISK1 1.Standard Installation assumes that you are installing the AppleTalk stack to connect to an Ethernet or Token-Ring network. 2.To enable remote connection to an ARA 3.0 compatible server (host) you must select Custom Installation, otherwise the protocol will not bind to a Dial-Up Adapter. 3.To install PC MACLAN onto a LocalTalk network, select Custom Installation and check the Network Transport option. This will give you the opportunity to add an ODI adapter. 4.After installing PC MACLAN, the AppleTalk protocol stack needs to be entered into the Windows 95/98 Registry. The installer will do this for you. Do not reboot your system until after this has been accomplished. B.If the protocol and client get removed from the Network Control Panel applet follow the steps listed below to setup the AppleTalk protocol and client for Ethernet or Token-ring networks: 1.Select the CONTROL PANEL from your computer 2.Select the Network ICON 3.Select the ADD button 4.Select Adapter (if there is one previously installed skip to #9) 5.From the manufacturer list choose your ethernet card's maker 6.From the list of adapters select the adapter you installed 7.Select OK 8.If you do not wish to connect to other PCs, remove the two Microsoft clients and the IPX/SPX protocol and the NETBEUI protocol 9.Select Add 10.Select Protocol 11.Select ADD 12.Under Manufacturers List box choose Miramar Systems, Inc. 13.Select the Miramar Systems AppleTalk protocol for NDIS3 and press OK 14.Select the ADD button 15.Select Client 16.Select ADD 17.Under Manufacturers List box choose Miramar Systems, Inc. 18.Select OK 19.Select OK again to enter the new values into the Windows registry 20.Select YES to Restart WINDOWS 9x C.To setup the ODI LocalTalk AppleTalk protocol and client do the following: 1.Select the CONTROL PANEL from your computer 2.Select the Network ICON 3.Select the ADD button 4.Select Adapter (if there is one previously installed skip to 9) 5.From the manufacturer list choose "(installed LocalTalk driver)" 6.From the Network Adapters list select "ODI LocalTalk Driver (via ATDRIVER.BAT)" 7.Select OK 8.Select Add 9.Select Protocol 10.Select ADD 11.Under Manufacturers List box choose Miramar Systems, Inc. 12.Select the Miramar Systems AppleTalk protocol for ODI and press OK 13.Select the ADD button 14.Select Client 15.Select ADD 16.Under Manufacturers List box choose Miramar Systems, Inc. 17.Select OK 18.Select OK again to enter the new values into the Windows registry. 19.Select YES to Restart WINDOWS 95 ----------------------------------------------------------------------------- II. Running in Demo mode The following are the limitations to PC MACLAN when in demonstration mode: 1.The duration is limited to 180 minutes after Windows is restarted. 2.Only one client connection to a Mac server is permited at a time. 3.Two Mac clients may log into the PC MACLAN Demo file server using the user name "Demo" with no password. 4.Printing may only be done to LaserWriters on the AppleTalk network. 5.A "Demo Version" impression (watermark) appears on every printed page. The Demonstration Mode is converted to a fully funtional PC MACLAN installation when a serial number is entered in the AppleTalk Settings applet. You do not need to uninstall PC MACLAN to convert from demo mode to serialized. ----------------------------------------------------------------------------- IIIa. Upgrading from Personal MACLAN v5.5x to v7.2 Please remove the File Server and Print Server from the Start-up Group prior to upgrading. You do not need to uninstall v5.5x from Windows 95 prior to installing. The File Server database in Personal MACLAN version 5.5x for Windows 95 is not compatible with version 6.1 (or greater). During installation the installer will detect the location of the previous version and will create backup files (extension .BAK). The first time the File Server is run, these .BAK files will be converted to the new database format which supports Long File Names. IIIb. Upgrading from PC MACLAN v6.x/v7.x to v7.2 Please remove the File Server and Print Server from the StartUp Group prior to upgrading. You do not need to uninstall PC MACLAN from Windows 95 prior to re-installing. You will need to run the backup utility on the File server to prevent the loss of resource and icon information on Macintosh files stored on PC volumes. Before performing the upgrade, if you use the File Server to save Macintosh files on your PC, you must backup the server system files. From the Server menu, select Backup System files and change the destination directory to any directory other than "." or "MACLAN6" or "PCMACLAN." From the registry export the following key to the same directory: HKLM\SOFTWARE\Miramar Systems, Inc.\File Server\Profiles\Sharepoints After completing the upgrade, copy the .BAK files to the PCMACLAN directory and change the extension to .DAT. Also, merge the exported .REG file back to the Registry. The next time the server is run the system files will be reported as corrupt and a rebuild will be requested. This is normal. If you are upgrading from a beta release of PC MACLAN v6.0, due to changes to the UNC path structure, you must delete your AppleTalk network printers before attempting to print. Re-establish your printers by double clicking the printer from the Network Neighborhood or by browsing in the Add Printer wizard. ============================================================================= IV. Unlisted Adapters information If you have a Network adapter that was not listed during Install then you will need to determine whether it came with NDIS or ODI drivers. --------------------------------------------------------------------------- A.For ODI unlisted adapters If you cannot locate your specific network adapter from the Install "Adapter selection list" perform the following STEPS: 1.Locate the ODI driver on the disk that came with your adapter. (XXXXXXXX.COM) 2.Copy the ODI driver file into the PC MACLAN Installation directory. Ex: Copy A:\ODI\XXXXXXXX.COM C:\PCMACLAN 3.Run INSTALL, select Custom install and check the Network Transport checkbox. From the Select Network Adapters and select UNLISTED adapter from the NET CARD list. 4.After INSTALL use a text editor like NOTEPAD and edit the NET.CFG file located in the PC MACLAN Installation directory and change all XXXXX text to the name of your ODI driver. 5.Using a text editor, edit the ATDRIVER.BAT file located in the PC MACLAN Installation directory & change XXXXX text to the name of your ODI driver. If your adapter has settings such as different interrupts, DMA, Memory Address, Port Address than those presented during installation it maybe necessary to edit the NET.CFG file located in the PCMACLAN directory. Example: LINK SUPPORT BUFFERS 9 628 MEMPOOL 16K MAX BOARDS 4 LINK DRIVER XXXXX ----->XXXXX change to your drivers name # UNLISTED ADAPTER NAME INT #1 9 ----->INTERRUPT change 9 to your value PORT #1 200 8 ----->PORT ADDRESS change 200 to your value DMA #1 3 ----->DMA Channel change 3 to your value MEM #1 C000 10 ----->Memory Address change C000 10 to your value FRAME ETHERNET_SNAP FRAME ETHERNET_II FRAME ETHERNET_802.2 FRAME ETHERNET_802.3 PROTOCOL IPX 0 ETHERNET_802.3 PROTOCOL APPLETALK 80007809B ETHERNET_SNAP PROTOCOL AARP 80F3 ETHERNET_SNAP For Token-ring, change all "ETHERNET..." text to "TOKEN-RING..." for example: instead of "FRAME ETHERNET_SNAP" enter "FRAME TOKEN-RING_SNAP" ---------------------------------------------------------------------------- B.For NDIS3 unlisted adapters. 1.Run the Network Applet from Windows 95 Control Panel. 2.Select Add 3.Select Add adapter to see if your Network adapter is listed. If it's unlisted follow the manufacturers' directions on installing NDIS3 drivers for Windows95. 4.If you find your adapter, select it. 5.If you do not need to connect to other PCs or to Netware servers, remove the Netbeui and IPX/SPX protocols. Be sure to check your Windows 95 documentation for details. ============================================================================= V. ERRORS during INSTALLATION 1.PC MACLAN may have detected incompatible AppleTalk drivers on your system. Please remove all items as listed below from your system files. Install reports "Found Farallon" IN AUTOEXEC.BAT "aboth.bat" may appear as "call ABOTH.BAT" "aprint.bat" may appear as "call APRINT.BAT" "afiles.bat" may appear as "call AFILES.BAT" "aarp.com" "atalk.com" "pntvdd.exe" IN FILE DIRECTORIES Locate your "c:\phonenet" directory and rename "net.cfg" to "net.xxx". IN SYSTEM.INI Edit & remove: "PhoneNETMemoryPool" statement from the "386Enh" section 2. PC MACLAN has detected a previous installation. Drivers are incompatible with version 7.2 Found earlier version Personal MACLAN Connect/PC MACLAN IN AUTOEXEC.BAT ATDRIVER.BAT MLDRIVER.BAT LMSTART.BAT 3. PC MACLAN has detected AppleShare for Windows installation. This is compatible with PC MACLAN v7.2 Found AppleShare IN AUTOEXEC.BAT "ATDRIVER.BAT" 4. Norton Navigator Disable Norton Navigator before installing as it will prevent installation. You can enable it after Install has completed. 5. The AppleTalk driver was not found. The file server or print server are in the start-up group. These must be removed before upgrading to PC MACLAN v7.2. 6. Failed to load ATKNP32.DLL COPSTalk has been installed on this system. Check Miramar's support Knowledge Base on the web for more information. 7. SUR_REG CREATE KEY FAILED Disable Cleansweep prior to installing. ============================================================================= VI. ERRORS during system OPERATION --------------------------------------------------------------------------- NOTE: For a more complete listing, Miramar Systems, Inc. maintains a Knowledge Base accessible from our Web site at http://www.miramarsys.com 1. "Need to run LSL.COM" This error will occur if you are running Novell Netware and Install detected LSL.COM in system memory. FIX: Edit your AUTOEXEC.BAT and move the "CALL <path>\ATDRIVER.BAT" statement AFTER the line(s) that execute the LSL and MLID statements. Example: Before CALL ATDRIVER.BAT PATH C:\DOS;C:\WINDOWS C:\NETWARE\LSL C:\NETWARE\3C5X9 etc.... After PATH C:\DOS;C:\WINDOWS C:\NETWARE\LSL C:\NETWARE\3C5X9 CALL ATDRIVER.BAT etc.... NOTE:All network device drivers are provided for the exclusive use of PC MACLAN using the manufacturer's proprietary network adapters. Using a manufacturer's network drivers with another manufacturers' network adapter is strictly prohibited. 2. "Access Denied" This error may occur when a file is copied to a "Drop Box" from a DOS box. The operating system attempts to set the time/date of the file to its original value after the file has been successfully copied. This operation fails and the system returns the error condition. The file has been copied to the "Drop Box" but has the current time/date. 3. To browse for network printers from within the Add Printer wizard you'll need to get and install the Win 95 Service Pack. Users with the OSR 2 release or with Windows 98 will not have this problem. 4. "Server not found" errors: Macintosh servers containing a '=' (i.e. equal sign) cannot be accessed correctly. 5. "Local device is already in use." Folder name is not accessible. This error message is generally due to insufficient permissions set on the folder you are attempting to access. ============================================================================== VII. Incompatible Adapters (ODI & NDIS3) Some older adapters have not had their ODI driver updated by the manufacturer and have become out of spec to the current requirements of ODI and NDIS3. The following list contains the adapter, the problem you may experience and a possible workaround. NE1000 Problem: Incompatible, obsolete drivers. solution: None INTEL ETHER EXPRESS PRO Problem: Windows freezes at splash/intro screen Windows freezes on re-entry after closing Solution: 1.If running Windows for WorkGroups select the ODI protocol 2.Obtain the latest NDIS3 driver. APPLE LOCALTALK Problem: Incompatible, obsolete drivers. Solution: Use an Apexx PCTALK adapter instead. TOPS/SITKA CARDS Problem: Incompatible, obsolete drivers. solution: Use an Apexx PCTALK adapter instead. SMC 8216 Problem: Can cause a Page Fault (Blank screen with flashing cursor) if the cable is disconnected from adapter during a file copy. Solution: Obtain the latest NDIS3 drivers from SMC. ODI does not have this problem. SMC 9432 Problem: When using the SMC Etherpower II (9432-TX) adapter there is a known issue with our 6.x and 7.x File Clients. Looking in the Entire Network you can see all AppleTalk resources, double click on a Mac, type the login name and password and press OK - you will immediately receive a blue screen OE exception error. This is due to an incompatibility between the 9432-TX drivers and our protocol stack. Solution: Obtain a different network adapter. We have not been able to resolve this incompatibility. ============================================================================= VIII. Performance Issues Some network adapters drivers may not perform to your expectations. Miramar recommends that you always use the latest drivers available from the manufacturer. Make sure that there are no conflicts with Memory, Interrupts, DMA etc... as this can also cause poor performance. The higher the CPU power the better PC MACLAN will perform. If your network uses 100BaseT and appears to have slowdowns or other performance problems when working between PCs and Macs, please upgrade the MAC OS to 8.5. Apple has reported that numerous problems associated with 100BaseT networking have been fixed in MacOS 8.5. ============================================================================= IX. AFP 2.2 and Reporting available disk space on large drives Apple recently updated the AFP specification to accommodate large disk drives. Both the server and the client must support the AFP 2.2 specification and the Windows environment must also support calculations for large disks. For a windows 95/98 AppleTalk client to see correct drive space reported on a Mac with a harddisk over 2.0 GB, the Mac must be running AppleShare IP versions 6.0 or 6.1. For a Mac to see correct drive space reported on a Windows computer with a harddisk larger than 2.0GB, the PC Maclan v7.2 File Server must be running on a version of Windows newer than (but not including) 4.00.950a. AND the Mac must be using AppleShare Client version 3.8 or newer. ============================================================================= X.Uninstalling from Windows 95/98 via a floppy installation To Uninstall from Windows 95/98: 1.Throw away any shortcuts to PC MACLAN executables. 2.Delete any network printers connected via AppleTalk 3.Run the Add/Remove Programs applet in the Control Panel, select PC MACLAN v7.2 and press the Add/Remove button. When requested, place disk 1 into the specified drive and select Uninstall. 4.When asked to restart your computer, select "Yes" then remove disk 1. 5.When "Starting Windows95 ..." is seen on the monitor, re-insert disk 1. Note: The file MirmarRegistration.txt is not automatically removed during uninstall and this issue will prevent the install program from deleting the pcmaclan program folder. ============================================================================= D I S C L A I M E R Miramar Systems makes no guarantees as to the compatibility of any third party device drivers for operability with Miramar products. IN NO EVENT SHALL MIRAMAR SYSTEMS, INC. HAVE ANY LIABILITY FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, BUSINESS INTERRUPTION, LOSS OF USE OF EQUIPMENT, LOSS OF DATA OR COSTS OR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, ARISING IN ANY WAY, OR UNDER ANY CAUSE OF ACTION, WHETHER OR NOT MIRAMAR SYSTEMS, INC. OR AN AUTHORIZED REPRESENTATIVE OF MIRAMAR SYSTEMS,INC. HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THESE LIMITATIONS SHALL APPLY NOTWITH- STANDING THE FAILURE OF THE ESSENTIAL PURPOSE OF ANY LIMITED REMEDY.